Task: Determine The Test Strategy (AST)
Purpose
To decide, based on the insight into the risk levels associated with the object parts/characteristics of the system, on the test types to be used, and on the depth of testing for each (combination of) characteristic/object part of the system.
Relationships
Main Description

Method of operation

In defining the strategy for a test level, the choice is made about the test types and thoroughness of testing, i.e. the extent to which the combinations of characteristics and object parts are tested. This is dependent on the risk estimate from the PRA, or rather the degree to which the client wishes to cover these risks, and how much time/money he allocates for it.

To this end, the test manager makes a proposal for each combination of object part/characteristic in respect of the required test types and depth of testing.

Test types

In this, the test manager specifies what is to be tested out of a particular object part-combination. At its simplest, this is the test of a quality characteristic, e.g. a functionality test or performance test, but often it is possible, and necessary, to provide more insight. Other test types are associated with the quality characteristic functionality, e.g. the multi-user test, regression test or chain test.

Testing depth

As regards the depth of testing, a choice is made from the following possibilities:

●●● Thorough dynamic testing
●●   Average dynamic testing
●     Light dynamic testing
S     Static testing: Checking and inspecting products without software being run
I      Implicit testing: Testing in conjunction with another test type without making explicit test cases; only observable defects are documented.
−     If there is nothing in a cell, this means that the relevant evaluation or test level can ignore the characteristic.

An initial setup of the strategy is often possible in the PRA session or the PRA, and these steps of the Strategy definition can be combined. If this doesn’t work, then the test manager makes a proposal.

A point to note is that when the MTP indicates a thoroughness of ●●● for a particular test level (e.g. ST) or a particular combination of characteristic/object part, this doesn’t mean that, in the ST, the entire system, or the combination of characteristic/object part, should be tested in the greatest possible coverage, but that testing is required in greater depth than average. This should also be evident from the MTP notes.

Products

The test strategy, established in the test plan, with a brief description of the planned test types and an indication of the importance per characteristic/object part.

Techniques

Strategy determination (as described above).

Illustrations
More Information